Clarify the docs for args in asyncio callbacks#143873
Clarify the docs for args in asyncio callbacks#143873akx wants to merge 3 commits intopython:mainfrom
args in asyncio callbacks#143873Conversation
akx
requested review from
1st1,
asvetlov,
kumaraditya303 and
willingc
as code owners
bedevere-app
bot
added
docs
|
|
||
| Arrange for *func* to be called in the specified executor. | ||
| Arrange for *func* to be called in the specified executor | ||
| with *args* being passed as positional arguments. |
There was a problem hiding this comment.
Can we use the same formulation as elsewhere (that is use either "passing...." or "with args ...")
|
Updating branch to fix the CI. |
kumaraditya303
left a comment
kumaraditya303
left a comment
There was a problem hiding this comment.
awaiting changes for Bénédikt's review
|
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase |
4 participants
While working on asyncio-related things, my eyes somehow skipped over the "keyword arguments" part of the sentence about
functools.partial, andargswasn't at all documented foradd_signal_handler.Hence, this PR gently clarifies the documentation for
*argsin asyncio loop callbacks and unifies all of the places referring tofunctools.partialto have similar verbiage.I think this is a trivial enough documentation improvement that it doesn't require an issue, but let me know if not so.
📚 Documentation preview 📚: https://cpython-previews--143873.org.readthedocs.build/